| Main Description |
Example of System Test (ST)
RC MTP = Risk class assigned to the characteristic from within the master test plan
ST MTP = Depth of testing assigned to the test (in this case, the system test) from within the master test plan
n/a = not applicable, in the master test plan risk class and depth are not assigned to the characteristic, but to the
combination object part/characteristic
A = High risk class
B = Average risk class
C = Low risk class
The risk classes are taken from the PRA of the master test plan or (in more detail) from the PRA of the test level
itself.
The test manager then supplies this table with the necessary explanations. In the above example, a functional test is
to be carried out for subsystems 1 and 2 in respect of the new and changed functionality, and a regression test in
respect of the unchanged parts will be furnished. Following the separate testing of subsystems 1 and 2, the total
system will be tested as regards integration aspects; a multi-user test will also take place. Performance will be
tested in the non-representative ST environment for a limited number of situations.
UAT example
In the above example, for subsystem 1 a functional test is performed again, using a number of the test cases from the
ST, but in the AT environment. If several deliveries are made, a regression test on the total system takes place. A
usability test in the own environment is carried out and in other tests an implicit test of user-friendliness is
carried out. The authorisation matrix is evaluated as regards correct content for subsystems 1 and 2. Also, the
business processes, or subprocesses, related to subsystems 1 and 2 are simulated by means of running user scenarios.
Subsequently, the operation of the total system is tested in combination with the business processes. A light
penetration test is also supplied.
|
